Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

check-cherry-picks.sh maintainer script: fix handling of cherry-pick-less branches #303211

Merged
merged 2 commits into from
Apr 10, 2024

Conversation

risicle
Copy link
Contributor

@risicle risicle commented Apr 10, 2024

Description of changes

PRs with no commits mentioning cherry-picks will produce an empty output from the git command. This behaviour will have changed when I chose a different iteration approach shortly before merging 😿

This should fix situations like #303093

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Add a 👍 reaction to pull requests you find important.

@risicle risicle requested a review from LeSuisse April 10, 2024 21:04
Copy link
Contributor

@LeSuisse LeSuisse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made #303192 but I'm not sure which way we should prefer.

Do we still need the condition L31?

@LeSuisse LeSuisse merged commit b607b94 into NixOS:master Apr 10, 2024
6 of 7 checks passed
Copy link
Contributor

Copy link
Contributor

Git push to origin failed for release-23.11 with exitcode 1

Copy link
Contributor

Backport failed for release-23.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-23.11
git worktree add -d .worktree/backport-303211-to-release-23.11 origin/release-23.11
cd .worktree/backport-303211-to-release-23.11
git switch --create backport-303211-to-release-23.11
git cherry-pick -x b612366abc32edc61e86d0fcc0f4a08cabcf5212 dc4f2184327d7b04edda404fa8562ba5e3e17755

1 similar comment
Copy link
Contributor

Backport failed for release-23.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-23.11
git worktree add -d .worktree/backport-303211-to-release-23.11 origin/release-23.11
cd .worktree/backport-303211-to-release-23.11
git switch --create backport-303211-to-release-23.11
git cherry-pick -x b612366abc32edc61e86d0fcc0f4a08cabcf5212 dc4f2184327d7b04edda404fa8562ba5e3e17755

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants